Method and apparatus for reporting UE capabilities using manufacturer-specific identifier of UE capability in next mobile communication systems

ABSTRACT

A communication technique for convergence of the 5G communication system for supporting higher data transmission rate after the 4G system with IoT technologies and a system thereof. Certain embodiments may be applied to intelligent services based on the 5G communication technologies and the IoT-associated technologies (for example, smart home, smart building, smart city, smart car or connected car, health care, digital education, retail services, security and safe-associated services, etc.). A method and an apparatus which can substitute reporting UE capabilities by use of an identifier of the UE, without reporting the overall UE capabilities in a method of reporting UE&#39;s own capability.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based on and claims priority under 35 U.S.C. § 119to Korean Patent Application No. 10-2019-0051794 filed on May 2, 2019 inthe Korean Intellectual Property Office, the disclosure of which isincorporated by reference herein in its entirety.

BACKGROUND 1. Field

The present disclosure relates to mobile communication systems, and inparticular, to a method and an apparatus being capable of substitutingreporting of UE capability by use of an identifier of the UE, withoutreporting the overall UE capabilities in a reporting method of the UE'sown capability.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a “Beyond 4G Network” or a“Post LTE System”. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), full dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud radio access networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,coordinated multi-points (CoMP), reception-end interference cancellationand the like. In the 5G system, hybrid FSK and QAM modulation (FQAM) andsliding window superposition coding (SWSC) as an advanced codingmodulation (ACM), and filter bank multi carrier (FBMC), non-orthogonalmultiple access (NOMA), and sparse code multiple access (SCMA) as anadvanced access technology have also been developed.

The Internet, which is a human-centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofeverything (IoE), which is a combination of the IoT technology and thebig data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including, without limitation, smarthome, smart building, smart city, smart car or connected cars, smartgrid, health care, smart appliances and advanced medical servicesthrough convergence and combination between existing informationtechnology (IT) and various industrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, machine type communication (MTC), andmachine-to-machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud radioaccess network (RAN) as the above-described big data processingtechnology may also be considered an example of convergence of the 5Gtechnology with the IoT technology.

Where a base station requests a UE for its capability and the UE reportsits capability information in response thereto, a method for performingthe concerned operation with reduction of signaling overhead isrequired.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

An aspect of the disclosure is to provide examples of methods forsubstituting reporting of UE capability by use of information of anidentifier which is specified for a UE having the same UE capability, ina series of procedures in which the UE receives a request for UEcapability from a base station and reports the UE capability to the basestation in the NR system. In certain embodiments, the above-describedmethod may employ use of a manufacturer-specific UE identifier and useof a PLMN-specific UE identifier. In particular, the disclosure providesexamples of general operations for methods of delivering UE capabilityby use of the manufacturer-specific UE identifier.

Another aspect of the disclosure is, for a specific UE belonging to abase station which supports both a basic uplink and an additional uplinkin the NR system, to provide examples of allowing the additional uplinkto be released.

In accordance with an aspect of the disclosure, certain methodsaccording to this disclosure are performed by a terminal in a wirelesscommunication system includes receiving, from a base station,information configuring an uplink (UL) of the base station and asupplementary uplink (SUL) of the base station for the terminal;communicating with the base station on the UL or the SUL, based on theinformation configuring the UL and the SUL for the terminal; receiving,from the base station, information on reconfigurationwithsync; andreleasing the SUL, in case that the information onreconfigurationwithsync does not include information associated with aSUL configuration.

In accordance with an aspect of the disclosure, certain methodsperformed by a base station in a wireless communication system includetransmitting, to a terminal, information configuring an uplink (UL) ofthe base station and a supplementary uplink (SUL) of the base stationfor the terminal; communicating with the terminal on the UL or the SUL,based on the information configuring the UL and the SUL for theterminal; and transmitting, to the terminal, information onreconfigurationwithsync, wherein the SUL is released, in case that theinformation on reconfigurationwithsync does not include informationassociated with a SUL configuration.

In accordance with certain embodiments of this disclosure, a terminal ina wireless communication system comprises a transceiver; and acontroller configured to: receive, via the transceiver from a basestation, information configuring an uplink (UL) of the base station anda supplementary uplink (SUL) of the base station for the terminal;communicate with the base station on the UL or the SUL, based on theinformation configuring the UL and the SUL for the terminal; receive,via the transceiver from a base station, information onreconfigurationwithsync; and release the SUL, in case that theinformation on reconfigurationwithsync does not include informationassociated with a SUL configuration.

In accordance with some embodiments as disclosed herein, a base stationin a wireless communication system comprises a transceiver; and acontroller configured to: transmit, via the transceiver to a terminal,information configuring an uplink (UL) of the base station and asupplementary uplink (SUL) of the base station for the terminal;communicate with the terminal on the UL or the SUL, based on theinformation configuring the UL and the SUL for the terminal; andtransmit, via the transceiver to a terminal, information onreconfigurationwithsync, wherein the SUL is released, in case that theinformation on reconfigurationwithsync does not include informationassociated with a SUL configuration.

According to some embodiments of the disclosure, in some methods bywhich a NR UE reports its capability, there is an effect that reportingof UE capability can be substituted for using an identifier of the UE,without reporting the overall UE capabilities.

Also, methods of configuration of a base station as provided by someembodiments of this disclosure support a basic uplink and an additionaluplink in a cell. However, as the specific UE is allowed to release theadditional uplink, the concerned UE can do transmission and reception ofdata through the basic uplink. In this regard, there is an effect suchthat more wireless resources can be used or more capabilities of UE canbe used.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1A illustrates an example of a structure of an LTE system,according to various embodiments of this disclosure;

FIG. 1B illustrates an example of a wireless protocol structure in theLTE system, according to certain embodiments of this disclosure;

FIG. 1C illustrates an example of a structure of a next generationmobile communication system according to certain embodiments of thisdisclosure;

FIG. 1D illustrates an example of a wireless protocol structure of anext generation mobile communication system according to variousembodiments of this disclosure;

FIG. 1E illustrates an example of a message structure for reporting ofUE capability in a NR system according to various embodiments of thisdisclosure;

FIG. 1F illustrates an example of registration and deregistration of aUE with a 5G core network in a NR system according to certainembodiments of this disclosure;

FIG. 1G illustrates an example of an operation to confirm UE capabilityby use of a manufacturer-specific identifier of UE capability, (referredto herein as a first reference example) according to certain embodimentsof this disclosure;

FIG. 1H illustrates an example of an operation when confirmation of UEcapability by use of a manufacturer-specific identifier of UE capabilityfails, (referred to herein as a second reference example) according tovarious embodiments of this disclosure;

FIG. 1I illustrates an example of operations to request amanufacturer-specific identifier of UE capability and report the same,in particular, to generate the manufacturer-specific UE capability,according to certain embodiments of his disclosure;

FIG. 1J illustrates an example of operations by the UE to receive arequest for manufacturer-specific UE capability and an identifierthereof and report them, according to certain embodiments of thisdisclosure;

FIG. 1K illustrates an example of operations by a base station and acore network to request for manufacturer-specific UE capability and anidentifier thereof and receive a report therefor, according to certainembodiments of this disclosure;

FIG. 1L illustrates, in block diagram format, an example a configurationof a UE according to various embodiments of this disclosure;

FIG. 1M illustrates, in block diagram format, an example of aconfiguration of a base station according to various embodiments of thisdisclosure;

FIG. 2A illustrates an example of a structure of an LTE system,according to certain embodiments of this disclosure;

FIG. 2B illustrates an example of a wireless protocol structure in theLTE system, according to certain embodiments of this disclosure;

FIG. 2C illustrates an example of a structure of the next generationmobile communication system according to some embodiments of thisdisclosure;

FIG. 2D illustrates an example of a wireless protocol structure of thenext generation mobile communication system according to someembodiments of this disclosure;

FIG. 2E illustrates an example of procedures by which a base stationtransmits cell-based uplink configuration to the UE and thereafterrelease the specific uplink configuration, according to variousembodiments of this disclosure;

FIG. 2F illustrates an example of operations by the UE when release ofthe UE-based uplink in a specific cell is applied, according to someembodiments of this disclosure;

FIG. 2G illustrates an example of operations by the base station when amethod to release the UE-based uplink in a specific cell is applied,according to certain embodiments of this disclosure;

FIG. 2H illustrates, in block diagram format, an example of an internalstructure of the UE according to various embodiments of this disclosure;and

FIG. 2I illustrates, in block diagram format, an example of aconfiguration of the base station according to certain embodiments ofthis disclosure.

DETAILED DESCRIPTION

FIGS. 1A through 2I, discussed below, and the various embodiments usedto describe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

Hereinafter, operation principles of certain embodiments according tothis disclosure will be described in detail in conjunction with theaccompanying drawings. In the following description of the disclosure, adetailed description of known functions or configurations incorporatedherein will be omitted when it may make the subject matter of thedisclosure rather unclear. The terms which will be described below areterms defined in consideration of the functions in the disclosure, andmay be different according to users, intentions of the users, orcustoms. Therefore, the definitions of the terms should be made based onthe contents throughout the specification. In the following description,terms for identifying access nodes, terms referring to network entities,terms referring to messages, terms referring to interfaces betweennetwork entities, terms referring to various identifiers and the likeare illustratively used for the sake of convenience. Therefore, thedisclosure is not limited by the terms as used below, and other termsreferring to subjects having equivalent technical meanings may be used.

In the following description, the disclosure uses terms and namesdefined in 3rd generation partnership project long term evolution (3GPPLTE) standards for the convenience of description. However, thedisclosure is not limited by these terms and names, and may be appliedin the same way to systems that conform to other standards.

FIG. 1A illustrates an example of a structure of an LTE system,according to various embodiments of this disclosure.

Referring to the non-limiting example of FIG. 1A, a wireless accessnetwork of an LTE system includes a next generation base station(Evolved node B; hereinafter referred to as “eNB”, “Node B” or “basestation”) (1 a-05, 1 a-10, 1 a-15, 1 a-20), an MME (Mobility ManagementEntity, 1 a-25), and S-GW (Serving-Gateway) (1 a-30). A user equipment(hereinafter referred to as “UE”) (1 a-35) connects to an externalnetwork via eNB (1 a-05 to 1 a-20) and S-GW (1 a-30).

In the non-limiting example of FIG. 1A, eNB (1 a-05 to 1 a-20)corresponds to an existing node B of the UMTS (Universal MobileTelecommunication System) system. The eNB is connected to the UE (1a-35) via a wireless channel and performs a more complex role than theexisting node B. In the LTE system, as all user traffic, includingreal-time services such as VoIP (Voice over IP) via an Internet protocolare served via a shared channel, a device for collecting and schedulingstate information such as buffer state of UEs, available transformationpower state, channel state, etc. is required. As such a device, the eNB(1 a-05 to 1 a-20) is used.

According to some embodiments, one eNB usually controls a number ofcells. In order to realize a transmission speed of 100 Mbps, the LTEsystem uses, for example, orthogonal frequency division multiplexing(hereinafter referred to as “OFDM”) in 20 MHz bandwidth as a wirelessaccess technology. Also, the LTE system applies modulation schemeadaptive to a channel state of the UE and adaptive modulation & coding(hereinafter referred to as “AMC”) to determine a channel coding rate.S-GW (1 a-30) is a device which provides data bearer, generating orremoving the data bearer according to control of an MME (1 a-25). MME (1a-25) is a device which functions various controls as well as mobilitymanagement for a UE and is connected to a number of base stations.

FIG. 1B illustrates an example of a wireless protocol structure in theLTE system according to various embodiments of this disclosure.

Referring to the non-limiting example of FIG. 1B, a wireless protocol ofthe LTE system includes PDCP (packet data convergence protocol) (1 b-05,1 b-40), RLC (radio link control) (1 b-10, 1 b-35), and MAC (mediumaccess control) (1 b-15, 1 b-30) at UE and eNB, respectively. PDCP (1b-05, 1 b-40) operates to compress and restore an IP header, etc. Thefunctions of PDCP comprise:

-   -   Header compression and decompression (ROHC only)    -   Transfer of user data    -   In-sequence delivery of upper layer PDUs at PDCP        re-establishment procedure for RLC AM    -   For split bearers in DC (only support for RLC AM): PDCP PDU        routing for transmission and PDCP PDU reordering for reception    -   Duplicate detection of lower layer SDUs at PDCP re-establishment        procedure for RLC AM    -   Retransmission of PDCP SDUs at handover and, for split bearers        in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

Radio Link Control (hereinafter referred to as “RLC”) (1 b-10, 1 b-35)reconstructs PDCP PDU (Packet Data Unit) in appropriate sizes andperforms ARQ operation, etc. The functions of RLC comprise:

-   -   Transfer of upper layer PDUs    -   Error Correction through ARQ (only for AM data transfer)    -   Concatenation, segmentation and reassembly of RLC SDUs (only for        UM and AM data transfer)    -   Re-segmentation of RLC data PDUs (only for AM data transfer)    -   Reordering of RLC data PDUs (only for UM and AM data transfer    -   Duplicate detection (only for UM and AM data transfer)    -   Protocol error detection (only for AM data transfer)    -   RLC SDU discard (only for UM and AM data transfer)    -   RLC re-establishment

As shown in the illustrative example of FIG. 1B, MAC (1 b-15, 1 b-30) isconnected to various RLC layer devices provided in a UE and performsoperations to multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUsfrom MAC PDUs. The functions of MAC comprise:

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs belonging to one or        different logical channels into/from transport blocks (TB)        delivered to/from the physical layer on transport channels    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

According to certain embodiments, a physical (“PHY”) layer (1 b-20, 1b-25) operates channel coding and modulation of upper layer data, makesthe data into OFDM symbols and transmits the OFDM symbols via a wirelesschannel and demodulates the OFDM symbols received via the wirelesschannel, operates channel-decoding thereof and transmits the decodeddata to the upper layer. Also in the physical layer, HARQ (Hybrid ARQ)is used to correct any additional error. Information on whether or not areceiver has received a packet transmitted from a transmitter istransmitted by using 1 bit. This is HARQ ACK/NACK information. DownlinkHARQ ACK/NACK information for the uplink transmission is transmitted viaa physical channel of PHICH (physical hybrid-ARQ indicator channel), anduplink HARQ ACK/NACK information for the downlink transmission may betransmitted via PUCCH (physical uplink control signal) or PUSCH(physical uplink shared channel).

The PHY layer may include one carrier or a plurality offrequencies/carriers. A technology to configure and use the plurality offrequencies simultaneously is called carrier aggregation (hereinafterreferred to as “CA”). According to various embodiments, a carrier isused for communication between a user equipment (UE) and a base station(E-UTRAN Node B, eNB). However, CA technology uses one carrier or aplurality of secondary carriers in addition to a primary carrier,thereby increasing the amount of transmission according to the number ofsecondary carriers. In LTE, the cell in the base station using theprimary carrier is PCell (Primary Cell) and the secondary cell is Scell(Secondary Cell).

In some embodiments, an RRC (radio resource control) layer is present inupper PDCP layers of the UE and the base station respectively, which isnot illustrated in the accompanying drawings. The RRC layer can make aconnection for wireless resource control and exchange configurationcontrol messages associated with measurement.

FIG. 1C illustrates an example of a structure of a next generationmobile communication system according to certain embodiments of thisdisclosure.

Referring to the non-limiting example of FIG. 1C, a wireless accessnetwork of the next generation mobile communication system includes anext generation base station (new radio node B; hereinafter referred toas “NR-NB”) (1 c-10) and a new radio core network or a next generationcore network (hereinafter referred to as “NG CN” (1 c-05). A new radiouser equipment (hereinafter referred to as “NR UE”) (1 c-15) connects toan external network via NR NB (1 c-10) and NR CN (1 c-05).

In the illustrative example of FIG. 1C, the NR NB (1 c-10) correspondsto the eNB (evolved node B) of the existing LTE system. The NR NB isconnected to a NR UE (1 c-15) via a wireless channel and can providemore excellent services than the existing node B. In certain embodimentsof the next generation mobile communication system, as all user trafficis served via a shared channel, a device for collecting and schedulingstate information including buffer state, available transmission powerstate, channel state, etc. of the UEs is required. In some embodiments,a NR NB (1 c-10) is used as such a device. In various embodiments, oneNR NB usually controls a plurality of cells. To realize ultra high speeddata transformation as compared with existing LTEs, the NR NB can have abandwidth equal to or greater than the existing maximum bandwidth and abeam forming technology can additionally be utilized by using orthogonalfrequency division multiplexing (OFDM). Also, adaptive modulation &coding (AMC) to determine a modulation scheme and a channel coding rateadaptive to the channel state of the UE is applied in some embodiments.A NR CN (1 c-05) functions to support mobility and set up bearer andQoS, etc. The NR CN is a device performing a variety of controls as wellas mobility management for the UE and is connected to a number of basestations. Also, the next generation mobile communication system can beassociated with the existing LTE system, and the NR CN is connected toMME (1 c-25) via a network interface. In certain embodiments, an MME isconnected to eNB (1 c-30), which is an existing base station.

FIG. 1D illustrates an example a wireless protocol structure of a nextgeneration mobile communication system according to various embodimentsof this disclosure.

Referring to the illustrative example of FIG. 1D, a wireless protocol ofthe next generation mobile communication system includes NR SDAP (1d-01, 1 d-45), NR PDCP (1 d-05, 1 d-40), NR RLC (1 d-10, 1 d-35), and NRMAC (1 d-15, 1 d-30) at UE and NR base station respectively.

The functions of NR SDAP (1 d-01, 1 d-45) comprise:

-   -   Transfer of user plane data    -   Mapping between a QoS flow and a DRB for both DL and UL    -   Marking QoS flow ID in both DL and UL packets    -   Reflective QoS flow to DRB mapping for the UL SDAP PDUs

With respect to an SDAP layer device, a UE may receive, through an RRCmessage, a configuration as to whether to use a header of the SDAP layerdevice or to use a function of the SDAP layer device for each PDCP layerdevice, each bearer, or each logical channel. Where the SDAP header isset, the SDAP layer device can instruct the UE to update or reset QoSflows of the uplink and the downlink and mapping information for databearer by a 1-bit NAS reflective QoS indicator and a 1-bit AS reflectiveQoS indicator of the SDAP header. The SDAP header may include QoS flowID information representing QoS. The QoS information may be used as dataprocessing priority, scheduling information, etc. to assist in thesmooth provision of services.

The functions of NR PDCP (1 d-05, 1 d-40) comprise:

-   -   Header compression and decompression: ROHC only    -   Transfer of user data    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   PDCP PDU reordering for reception    -   Duplicate detection of lower layer SDUs    -   Retransmission of PDCP SDUs    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

In some embodiments, the reordering function of the NR PDCP device is afunction to sequentially reorder PDCP PDUs received by the lower layerbased on PDCP SN (sequence number). This function may include a functionto transmit data to the upper layer in the reordered sequence or todirectly transmit data without considering the sequence, and a functionto record lost PDCP PDUs by reordering the sequence thereof. Inaddition, functions to report states of the lost PDCP PDUs to thetransmitter, and to request retransmission of the lost PDCM PDUs may beincluded.

The functions of an NR RLC (1 d-10, 1 d-35) comprise:

-   -   Transfer of upper layer PDUs    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   Error Correction through ARQ    -   Concatenation, segmentation and reassembly of RLC SDUs    -   Re-segmentation of RLC data PDUs    -   Reordering of RLC data PDUs    -   Duplicate detection    -   Protocol error detection    -   RLC SDU discard    -   RLC re-establishment

According to some embodiments, in-sequence delivery of the NR RLC deviceis a function to transmit RLC SDUs received from the lower layer to theupper layer in sequence, originally where one RLC SDU is segmented intoseveral RLC SDUs and the segmented RLC SDUs are received, and mayinclude a function to reassemble and transmit the received RLC PDUs maybe included. A function to reorder the received RLC PDUs based on RLC SNor PDCP SN, a function to reorder the sequence of the received RLC PDUsand record lost RLC PDUs, a function to report the states of the lostRLC PDUs to the transmitter, and a function to request retransmission ofthe lost RLC PDUs may also be included. Where there is any lost RLC SDU,a function to transmit only the RLC SDUs prior to the lost RLC SDU tothe upper layer in sequence may be included. Where a predetermined timerexpires even though there is any lost RLC SDU, a function to transmitall the RLC SDUs received before the timer starts to the upper layer insequence may be included. Where a predetermined timer expires eventhough there is any lost RLC SDU, a function to transmit all the RLCSDUs received up to now to the upper layer in sequence may be included.Also, the RLC PDUs may be processed in the order as they are received(in the order as arrived, without regard to the sequence of serialnumbers, sequence numbers, etc.) and delivered to the PDCP devicewithout regard to the sequence (out-of sequence delivery). In case ofsegments, segments are stored in a buffer or segments to be receivedlater are received, and thereafter they are reconstructed into acomplete single RLC PDU, which is then processed and delivered to thePDCP device. The NR RLC layer may not include a function ofconcatenation, or this function may be performed at the NR MAC layer orsubstituted for a multiplexing function of the NR MAC layer.

According to certain embodiments, an out-of sequence delivery functionof the NR RLC device is a function to deliver the RLC SDUs received fromthe lower layer directly to the upper layer without regard to thesequence thereof. Where an originally single RLC SDU is segmented intoseveral RLC SDUs and the segmented RLC SDUs are received, a function toreassemble them may be included. A function to store RLC SNs or PDCP SNsof the received RLC PDUs and order them in sequence, and record lost RLCPDUs may also be included.

As shown in the illustrative example of FIG. 1D, NR MAC (1 d-15, 1 d-30)can be connected to several NR RLC layer devices included in a UE, andmain functions of NR MAC may include one or more of the followingfunctions:

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

According to certain embodiments, a NR PHY layer (1 d-20, 1 d-25) canoperate channel coding and modulation of upper layer data, makes theminto OFDM symbols and transmits the OFDM symbols via a wireless channel,and demodulates the OFDM symbols received via the wireless channel,operates channel-decoding thereof and transmits the decoded data to theupper link.

FIG. 1E illustrates an example of a message structure for reporting ofUE capability in a NR system according to certain embodiments of thisdisclosure.

In certain embodiments, a UE (1 e-01) passes through a procedure toreport capabilities supported by the UE to a serving base station (1e-02) in a state that the UE is connected to the concerned base station.In some embodiments, at operation 1 e-05, the base station delivers tothe UE in a connected state a UE capability enquiry message thatrequests reporting of the UE capabilities. The message may include arequest by the base station for UE capability by each RAT type. The RATtype based request may include frequency band information as requestedaccording to the priority thereof. Also, the UE capability enquirymessage may request a plurality of RAT types in one RRC messagecontainer, or deliver to the UE the UE capability enquiry messageincluding the RAT type based request several times. That is, the UEcapability enquiry is repeated several times at 1 e-05 and the UE mayconstruct UE capability information messages corresponding thereto, andmatch a response to the concerned request and then report the response.In the next generation mobile communication system, UE capabilities forMR-DC including NR, LTE, EN-DC may be requested. For reference, the UEcapability enquiry message is generally delivered in an initial stageafter connection by the UE is made, but it may also be requested in anycondition when the base station requires.

At the above operation, the UE having received the request for reportingUE capability from the base station constructs the UE capabilityaccording to RAT type and frequency band information as requested by thebase station. An example of a method by the UE of constructing UEcapability in the NR system according to various embodiments will bedescribed below.

1. The UE may receive a request for a part or a whole of RAT types ofLTE, EN-DC and NR, as a request for UE capability, from the basestation, and may simultaneously receive a list of LTE and NR frequencybands. The UE constructs a band combination (BC) for EN-DC and NRstand-alone (SA). That is, based on the frequency bands requested asFreqBandList from the base station, a candidate list of BCs for EN-DCand NR SA is constructed. The concerned operation may be defined as anoperation of compiling a candidate band combination. Also, the priorityof the bands is determined in the sequence as described in theFreqBandList. The concerned operation may be performed one time withoutregard to the RAT type or operated repeatedly by each RAT type.

At the following operations, the concerned procedures are performed byeach RAT type, and operated according to the priority of NR, MR-DC, andLTE, in order:

2. If “eutra-nr-only” flag or “eutra” flag is set to the RAT type of theUE capability request message, the RAT types for NR SA BCs arecompletely removed from the candidate list of BCs constructed above.This may occur only where the LTE base station (eNB) requests “eutra”capability.

3. Thereafter, the UE removes fallback BCs from the candidate list ofBCs constructed at the above operation. The fallback BC is a case wherethe band corresponding to one SCell at minimum is removed from any superset of BCs. As the superset of BCs can already cover the fallback BC, itis possible to omit the fallback BC. In certain embodiments, thisoperation is also applied to EN-DC, that is, to LTE bands. The BCsremaining after this operation are the final “candidate list of BCs”.

4. The UE selects BCs suitable for the requested RAT types from thefinal “candidate list of BCs” and selects BCs to be reported therefrom.In this operation, the UE constructs supportedBandCombinationList in thepredetermined order. That is, the UE constructs BCs and UE capability tobe reported according to the sequence of rat-Types as previously set (nreutra-nr eutra). Also, featureSetCombination for the constructedspportedBandCombination is constructed, and a list of “candidate featureset combination” from the candidate list of BCs from which a list of thefallback BCs (including capabilities at the same or lower level) isremoved is constructed. According to various embodiments, the “candidatefeature set combination” includes the feature set combinations both forNR and EUTRA-NR BC and can be obtained from the feature set combinationof UE-NR-Capabilities and UE-MRDC-Capabilities containers.

5. Also, if the requested rat Type is eutra-nr and influences onsupportedBandCombination of the concerned EN-DC or MR-DC,featureSetCombinations are set adaptively to the concerned rat Type, andall are included in the two containers of UE-MRDC Capabilities and UE-NRCapabilities. However, in some embodiments, the feature set of NRincludes only UE-NR-Capabilities.

According to certain embodiments, after the UE capability isconstructed, the UE delivers a UE capability information messageincluding the UE capability to the base station at 1 e-10. Based on theUE capability received from the UE, the base station performs properscheduling and transmission and reception management to the concerned UEthereafter.

In certain embodiments, as part of the method for lowering thecomplexity in the existing procedure to request and report UEcapability, applied to the NR system, the disclosure considers a methodof enabling substitution of UE capability report by means of anidentifier (ID) representing the UE capability. Generally, UEs can beset to have the same UE capabilities according to UE serial numbersspecified by the manufacturer, or manufacturer-specific models. Also,where a base station and a core network have capability for theconcerned UE, it is possible to store and use the UE capability. If thesame UE capability is reported for the same UE models, the base stationand the core network would always receive the same UE capability reportfor the concerned UE model, and therefore, they can perform optimizationof the concerned operation. That is, if an identifier that representscapability of the concerned UE model is present and is reported by theUE, the base station and the core network can determine the concernedidentifier and retrieve the UE capability. In order to use an identifierthat represents the above UE capability, there are two options asdescribed below.

1. Manufacturer-specific identifier (ID) of UE capability: It ispossible to have an identifier for each manufacturer and each UE model(or for the UEs having the same UE capability among UEs of the samemanufacturer), which may be an identifier that uniquely representswireless link UE capability of the UE. Also, the concerned UE identifiermay represent the entire capability of the UE.

2. PLMN-specific identifier (ID) of UE capability: In a situation thatthe above manufacturer-specific identifier of UE capability is notprovided or the concerned base station and the core network cannotdiscern the identifier, an identifier that can be substituted thereforis required. The base station and the core network may provide aspecific identifier to the UE according to the UE capability. Theconcerned identifier should be applicable to the serving PLMN andallotted to PLMN specifically.

Among the operations to report UE capability through the twoidentifiers, certain embodiments according to this disclosure provideoperations for requesting and providing a manufacturer-specificidentifier of UE capability and confirming the UE capability.

FIG. 1F illustrates an example of registration and deregistration of aUE with a 5G core network in a NR system according to variousembodiments of this disclosure.

Referring to the non-limiting example of FIG. 1F, until before initiallyregistering a UE with a core network in the NR system, the UE is in astate of registration management (RM)-null with the concerned corenetwork in operation 1 f-05. Thereafter, if the concerned UE isactivated in N1 mode (a mode that can be connected to a 5G core network)in operation 1 f-20, the UE is present in a RM-DEREGISTRATION state withrespect to the concerned core network as in the operation 1 f-10. Thatis, this means that the concerned UE is capable of being connected tothe 5G core network, but the procedure to connect and register has notyet been completed. The UE in this state will try the procedure toconnect and register initially with the 5G core network in operation 1f-30. If this operation is completed, the UE is shifted to the state ofRM-REGISTRATION in operation 1 f-15. Thereafter, even if the UE performsa procedure to change the serving cell, etc., this is not an operationfor initial registration (1 f-40), and thus, the UE maintains the stateof RM-REGISTRATION. If the UE is deregistered in operation 1 f-35, theUE is shifted again to the state of RM-DEREGISTRATION. In certainembodiments, if deactivation of N1 mode is applied at the concernedstate, the UE is shifted to an RM-NULL state.

FIG. 1G illustrates an example of an operation to confirm UE capabilityby use of a manufacturer-specific identifier of UE capability, (referredto herein as a first reference example), according to variousembodiments of this disclosure.

Referring to the non-limiting example of FIG. 1G, a UE (1 g-01) in a RRCIDLE state can perform the RRC connection procedure with a specific NRbase station (gNB) (1 g-02) in operation 1 g-05. After the concerned RRCconnection procedure is performed, an NAS message including amanufacturer-specific identifier of UE capability (for example,ATTACH/REGISTRATION REQUEST) can be delivered to the core network (CN, 1g-03) to which the concerned base station is connected (1 g-10). Thecore network having received the message, discerns themanufacturer-specific identifier of UE capability and checks whether UEcapability corresponding to the concerned identifier is stored inoperation 1 g-15, and can confirm the UE capability mapped with theconcerned identifier. In certain embodiments, the manufacturer-specificidentifier of UE capability can be present as a table mapped with the UEcapability in the core network. Thereafter, the UE and the core networkperform a procedure to set up NAS security (authentication) in operation1 g-20, and the core network delivers the UE capability having beenknown as a result of confirming the manufacturer-specific identifier ofUE capability to the base station in operation 1 g-25. The message maybe included in an INITIAL CONTEXT SETUP REQUEST message (NAS message).At the above operation, the core network can deliver themanufacturer-specific identifier of UE capability received from the UEtogether. In various embodiments, at operation 1 g-30, the base stationstores the UE capability received from the core network, and thereafter,can reflect the UE capability in configuration of the RRC with the UE.As the concerned base station has been informed of the UE capabilitythrough these procedures, the base station may not trigger an operationto request UE for UE capability.

FIG. 1H illustrates an example of an operation when confirmation of UEcapability by use of a manufacturer-specific identifier of UE capabilityfails, (referred to herein as a second reference example) according tovarious embodiments of this disclosure.

Referring to the non-limiting example of FIG. 1H, a UE (1 h-01) in anRRC DEL state can perform the RRC connection procedure with a specificNR base station (gNB, 1 h-02) in operation 1 h-05. After the concernedRRC connection procedure is performed, an NAS message including amanufacturer-specific identifier of UE capability (for example,ATTACH/REGISTRATION REQUEST) can be delivered to a core network (CN) (1h-03) to which the concerned base station is connected (1 h-10). Thecore network, having received the message, discerns themanufacturer-specific identifier of UE capability and confirms whetherUE capability corresponding to the concerned identifier is stored inoperation 1 h-15, but cannot restore UE capability mapped with theconcerned identifier. For this operation, the manufacturer-specificidentifier of UE capability can be present in the form of a table mappedwith the UE capability in the core network. However, in this process,the manufacturer-specific identifier of UE capability provided by the UEmay not be stored and the concerned manufacturer-specific identifier ofUE capability may not be identified. Thereafter, the UE and the corenetwork perform a procedure to set up NAS security (authentication) inoperation 1 h-20. According to certain embodiments, at operation 1 h-25,the core network informs the base station of having no UE capability forthe UE and may deliver an INITIAL CONTEXT SETUP REQUEST message (NASmessage) requesting the UE capability to the base station. In the aboveoperation, the core network may deliver the manufacturer-specificidentifier of UE capability received from the UE together. In the aboveoperation, the base station confirms the manufacturer-specificidentifier of UE capability received from the core network. Ifrestoration is possible because the base station has UE capabilityinformation for the concerned identifier, the base station reports it tothe core network and thereafter may omit the UE capability requestingprocedure.

Referring to the non-limiting example of FIG. 1H, at operation 1 h-30,the base station confirms a request for the UE capability received fromthe core network and can trigger the UE capability request. That is, inoperation 1 h-35, a UECapabilityEnquiry message, including a RAT typefor the UE capability request and filtering information is delivered tothe UE. In operation 1 h-40, the UE reflects the concerned RAT type andfiltering information and constructs UE capability in response to the UEcapability request message received in operation 1 h-35, and deliversUECapabilityInformation message to the base station. In the aboveoperation, the UE may include the manufacturer-specific identifier of UEcapability in the UECapabilityInfomation message. In operation 1 h-45,the base station stores the UE capability information received from theUE. If the manufacturer-specific identifier of UE capability is receivedtogether from the UE, the concerned information is stored together. Inoperation 1 h-50, the base station delivers the UECapabilityInformationmessage received from the UE to the core network.

According to certain embodiments, the concerned UE capability mayinclude filtering information in different containers by each RAT typeand be delivered as it is (UE-CapabilityRAT-ContainerList together withfilter). In operation 1 h-55, the core network stores the UE capabilityreceived in the above operation and updates the UE capability mappingtable including the manufacturer-specific identifier of UE capabilityand UE capability. Thereafter, the stored UE capability can be appliedto the UE which provides the concerned manufacturer-specific identifierof UE capability.

FIG. 1I illustrates an example of operations to request amanufacturer-specific identifier of UE capability and report the same,in particular, to generate the manufacturer-specific UE capability,according to certain embodiments of this disclosure.

Referring to the non-limiting example of FIG. 1I, a UE (1 i-01) in anRRC IDLE state can perform a RRC connection procedure with a specific NRbase station (gNB, 1 i-02) in operation 1 i-05. After having performedthe concerned RRC connection procedure, the UE can deliver an NASmessage including a manufacturer-specific identifier of UE capabilityand a PLMN-specific identifier of UE capability (for example,ATTACH/REGISTRATION REQUEST) to a core network (CN) (1 i-03) to whichthe concerned base station is connected (1 i-10). In the aboveoperation, the PLMN-specific identifier of UE capability may beoptionally included in a case where the UE is in a previous connectionstate and the PLMN-specific UE capability allotted at the UE capabilitydelivery procedure is present, and it may be delivered in as a listincluding a plurality of items. Also, the PLMN-specific identifier of UEcapability may be selected in consideration of PLMN of the base stationcurrently in a state of being connected to the concerned UE. That is, insome embodiments, only an identifier for a PLMN which is the same as aserving cell can be reported. The core network having received the PLMNidentifier in operation 1 i-15 confirms the concernedmanufacturer-specific identifier of UE capability and the PLMN-specificidentifier of UE capability so as to confirm whether or not the UEcapability for the concerned identifier is stored, but may not restorethe UE capability mapped with the concerned identifier.

In certain embodiments, for this operation, the manufacturer-specificidentifier of UE capability and the PLMN-specific identifier of UEcapability and UE capabilities can be present as a mapping table in thecore network. However, in this process, the manufacturer-specificidentifier of UE capability and the PLMN-specific identifier of UEcapability, provided by the UE, may not be stored, and the concernedmanufacturer-specific identifier of UE capability and the PLMN-specificidentifier of UE capability may not be identified. Thereafter, the UEand the core network perform a procedure to set up NAS security(authentication) in operation 1 i-20, and inform the base station ofhaving no UE capability in operation 1 i-25. According to variousembodiments, an INITIAL CONTEXT SETUP REQUEST message (NAS message)requesting the UE capability may be delivered to the base station.

In the above operation, the core network can request the base stationfor full UE capability, which may be used in obtaining themanufacturer-specific UE capability. Also, the core network may delivertogether the manufacturer-specific identifier of UE capability havingbeen received from the UE. In the above operation, the base stationconfirms the manufacturer-specific identifier of UE capability havingbeen received from the core network. In certain embodiments, if the basestation has the UE capability information for the concerned identifierand it is possible to restore the UE capability, this is informed thecore network and the UE capability request procedure is omittedthereafter.

The base station confirms the UE capability request having been receivedfrom the core network in operation 1 i-30 and can trigger the UEcapability request. That is, a UECapabilityEnquiry message including RATtype requesting UE capability and filtering information is delivered tothe UE. The RRC message may include an option to request full UEcapability, that is, manufacturer-specific UE capability in a filter.That is, information for requesting full capability may be included inthe filtering information, or the information may be delivered in anunfiltered state by omitting filtering information by each RAT type, andthis may be used to mean that the entire UE information should bereported. Also, the RRC message may include an indicator to indicatewhether or not the UE can provide an identifier of UE capability.

According to various embodiments, if the UE possesses an indicator toindicate whether or not it can provide the UE capability identifier ofthe base station (or an indicator to indicate that themanufacturer-specific identifier of UE capability is not effective) andthe PLMN-specific identifier of UE capability mapped for a UE requestincluding RAT type and filtering, the UE can deliver aUECapabilityInformation message including only the concerned identifierto the base station in operation 1 i-40. However, if the UE does notpossess the PLMN-specific identifier of UE capability mapped for therequest from the base station, the UE reflects the concerned RAT typeand filtering information as in the existing procedure to generate andreport UE capability and constructs UE capability in operations 1 i-40and 1 i-45 and delivers the UECapabilityInformation message to the basestation. The below operation addresses a procedure according to whichthe UE is requested to report the manufacturer-specific UE capabilityfrom the base station and reports it.

According to some embodiments, at operation 1 i-40, the UE generates aUE capability message (UE capability information) for its own UEcapability request from the base station. If the concerned messageexceeds 9000 Bytes, which is the maximum size of PDCP PDU, segmentationis applied. That is, it can be known that the entire UE capabilityinformation message is segmented into segments having the size of 9000Bytes, and the last segment may be a segment having a remaining size(subtracting the sum of segmented RRC messages from the entire messagesize). Also, in a case of receiving a request for full UE capability inoperation 1 i-35 (full capability indicator or unfiltered request), theUE may include the entire UE capability and an indicator to indicatethat the UE capability to be reported is manufacturer-specific UEcapability or a manufacturer-specific identifier of UE capability.However, if the UE capability to be reported is not identical to themanufacturer-specific UE capability (Full UE capability), information(indicator) indicating that the UE capability to be reported is not themanufacturer-specific UE capability (full UE capability) is included inthe UE capability information message, which is delivered as it is (1i-45). According to certain embodiments, when the message is delivered,each RAT type is included in each container present inUE-CapabilityRAT-ContainerList, and is delivered as it is.

Where the UE delivers the manufacturer-specific identifier of UEcapability and UE capability together included in the message inoperation 1 i-45, the base station and the core network store UEcapability delivered, by associating it with the manufacturer-specificidentifier of UE capability, which may be interpreted and used as UEcapability thereafter. The below operation addresses a case where the UEdoes not deliver the manufacturer-specific UE capability in operation 1i-45. That is, where the UE delivers the UE capability together with anindicator indicating that the UE capability is not themanufacturer-specific UE capability, the UE capability informationdelivered in operation 1 i-50 is stored in an internal buffer (memory),together with the RAT type and filtering information requested by thebase station in association therewith. In addition, the UE can storeregistered PLMN information of the concerned serving cell connected fromthe system information (SIBI) having been received by the concernedserving cell. It is concluded that the UE stores the PLMN information,RAT type and filtering information, and reported UE capability in onegroup in the concerned operation.

As shown in the illustrative example of FIG. 1I, at operation 1 i-55,the base station delivers the UECapabilityInformation message havingreceived from the UE to the core network, and the concerned UEcapability includes filtering information in different containers byeach RAT type, which is transmitted as it is(UE-CapabilityRAT-ConainterList together with filter). Also, the messagemay include an indicator indicating that the UE capability is not themanufacturer-specific UE capability delivered from the UE. In operation1 i-60, the core network confirms the UE capability having been receivedat the above operation. Where the PLMN-specific identifier of UEcapability mapped with the UE capability reported by the UE for theconcerned filtering information and requested RAT type is present in thestored table, the concerned identifier is allotted as a PLMN-specificidentifier of UE capability. However, if the reported UE capability isnot possessed by the core network and is new, the core network may allota new PLMN-specific identifier of UE capability thereto.

According to some embodiments, at operation 1 i-65, the core networkdelivers to the UE the PLMN-specific identifier of UE capabilityattached adaptive to the UE capability reported by the UE by means of anNAS message (for example, ATTACH/REGISTRATION RESPONSE). The message mayinclude index information to indicate whether the identifier is anidentifier for any UE capability, or may be provided with the RAT typeand the filtering information mapped with the concerned UE capability. Areason why the concerned operation is required is because operations 1i-35, 1 i-40, and 1 i-45 are, in certain embodiments, not finished atone time, but they may be successively completed. For example, the basestation can deliver an NR-associated UE capability request for RAT typeand a filter in operation 1 i-35. After having received the concerned UEcapability from the UE in operation 1 i-45, the base station repeatsoperation 1 i-35 once again and requests EN-DC UE capability, andreceives report of the concerned UE capability in operation 1 i-45. Inthis case, the PLMN-specific identifiers of UE capability for the two UEcapabilities having successively been received should be distinguishedfor allocation. Therefore, index information to distinguish them (forexample, the first capability report of UE is set 1 and the secondcapability report of UE is set 2) may be included, or filing informationmay be delivered together.

Also, in certain embodiments, the method of the core network's allottinga PLMN-specific identifier of UE capability in operation 1 i-60 may beapplied differently depending upon network realization. For example, theconcerned UE capability may be specified only for a case where UEcapability reports for a specific UE are received and the number of UEreports to provide the same UE capability as the concerned UE capabilityis greater than a predetermined critical value (N) and the PLMN-specificidentifier of UE capability may be allotted thereto. That is, analgorithm not to allot a specific PLMN-specific identifier of UEcapability only with a few UE capability reports is required in certainembodiments.

Referring to the non-limiting example of FIG. 1I, at operation 1 i-70,the UE maps the PLMN-specific identifier of UE capability having beenreceived from the core network in operation 1 i-65 with the UEcapability storage group reported and stored by the UE in operation 1i-50 and newly stores the same. That is, the UE groups the PLMN-specificidentifier of UE capability, registered PLMN information, RAT type andfiltering information, and reported UE capability and stores them in onegroup at the concerned operation. Thereafter, a PLMN-specific identifierof UE capability allotted to represent the concerned UE capability canbe used. Also, in the above operation, the number of PLMN-specificidentifiers of UE capability that the UE can store may be limited. Ifthe UE capability for a new PLMN-specific identifier of UE capabilityshould be stored in a state that the UE has stored the predeterminednumber of PLMN-specific identifier of UE capability, the PLMN-specificidentifier of UE capability and the concerned UE capability group havingpreviously been stored can be erased and updated to new values. Also, incertain embodiments, it is possible to perform an operation to eraseinformation for the other PLMNs, remaining information only for the samePLMN in the above operation.

Thereafter, in operation 1 i-75, the core network can deliver to thebase station via an N1 message the PLMN-specific identifier of UEcapability having been delivered to the UE, and the base station storesthe PLMN-specific identifier of UE capability, registered PLMNinformation, RAT type and filtering information, and reported UEcapability in one group, based on the PLMN-specific identifier of UEcapability received in operation 1 i-80, the UE capability received inoperation 1 i-45, and the RAT type and filtering information having beendelivered to the UE in operation 1 i-35. Thereafter, where the UE usesthe PLMN-specific identifier of UE capability allotted to represent theconcerned UE capability, the base station having received thePLMN-specific identifier of UE capability may not trigger the UEcapability request.

FIG. 1J illustrates an example of operations by the UE to receive arequest for manufacturer-specific UE capability and an identifierthereof and report same, according to certain embodiments of thisdisclosure.

Referring to the non-limiting example of FIG. 1J, in operation 1 j-05,the UE can be camped on a specific serving cell and shifted to an RRCconnection state. Immediately after being connected to the concernedcell, the UE delivers an identifier of UE capability that the UEpossesses, via an NAS message (for example, INITIAL ATTACH/REGISTRATIONREQUEST message) to the core network connected to the concerned basestation in operation 1 j-10. The concerned identifier may include amanufacturer-specific identifier of UE capability and a PLMN-specificidentifier of UE capability. According to certain embodiments, in astate that the PLMN-specific identifier of UE capability has not beenallotted, only the manufacturer-specific identifier of UE capability canbe included. In operation 1 j-15, where the core network or the basestation fails to restore the UE capability for the identifier of UEcapability having been delivered by the UE, the UE will receive amessage that requests report of UE capability through the base station.The UE capability request message may include a filter that requestsfull UE capability. Otherwise, the message may be delivered in anunfiltered state, with omission of all the filtering information by eachRAT type, which may be used to mean that the full UE information is tobe reported.

In operation 1 j-20, the UE generates UE capability information inresponse to the above UE capability request message. That is,considering the filtering information having been requested in operation1 j-15, the UE capability message is generated. If the size of themessage is in excess of 9000 Bytes, the UE capability information issegmented, generating segmented information. Also, in certainembodiments, in operation 1 j-25, it is determined whether the UEcapability information generated in operation 1 j-20 is the same as themanufacturer-specific full UE capability (1 j-30). If the generated UEcapability information is same as the manufacturer-specific full UEcapability, the full capability information is reported in operation 1j-35. Simultaneously, an indicator indicating that the concerned UEcapability is the manufacturer-specific full UE capability, and themanufacturer-specific full UE capability, are included therein andreported to the base station.

As shown in the illustrative example of FIG. 1J, at operation 1 j-25, itis determined whether the UE capability information generated inoperation 1 j-20 is the same as the manufacturer-specific full UEcapability (1 j-30). Where the generated UE capability information isnot the same as the manufacturer-specific full UE capability, the UEincludes an indicator indicating that the reported UE capability is notthe manufacturer-specific full UE capability and delivers the same inoperation 1 j-40. In operation 1 j-45, the UE stores the reported UEcapability in a buffer (memory). Thereafter in operation 1 j-50, if aPLMN-specific identifier of UE capability is indicated via an NASmessage, the stored UE capability is associated with the PLMN-specificidentifier of UE capability and then stored and used. That is, in theconcerned operation, the UE stores the PLMN-specific identifier of UEcapability, registered PLMN information, RAT type and filteringinformation, reported UE capability in one group. Thereafter, thePLMN-specific identifier of UE capability allotted to represent theconcerned UE capability can be used.

Also, in the above operation, the number of PLMN-specific identifiers ofUE capability stored by the UE may be limited. If the UE capability fora new PLMN-specific identifier of UE capability should be stored in astate that the UE has stored the predetermined number of PLMN-specificidentifiers of UE capability, the PLMN-specific identifier of UEcapability and the concerned UE capability group having previously beenstored can be erased and updated to new values. Also, it is possible toperform an operation to erase information for the other PLMNs, remaininginformation only for the same PLMN in the above operation.

FIG. 1K illustrates an example of operations by a base station and acore network to request for manufacturer-specific UE capability and anidentifier thereof and receive a report therefor, according to variousembodiments of this disclosure.

As shown in the non-limiting example of FIG. 1K, at operation 1 k-05, ifa specific UE is camped on a concerned cell, a base station performs anRRC connection procedure and can shift the UE to a connected state. Acore network connected to a base station can receive an identifier of UEcapability that the UE possesses via an NAS message (for example,ATTACH/REGISTRATION REQUEST message). The concerned identifier mayinclude a manufacturer-specific identifier of UE capability and aPLMN-specific identifier of UE capability. In certain embodiments, in astate that no PLMN-specific identifier of UE capability is allotted,only the manufacturer-specific identifier of UE capability may beincluded. In operation 1 k-10, the core network determines whether theUE has UE capability based on the received identifier. If the concernedUE has no manufacturer-specific UE capability, the core network caninstruct the base station to start a procedure to request the requiredUE capability. The base station can receive an indicator requesting thefull UE capability from the core network at the concerned operation, orthe core network may allow any necessity for the full UE capability tooccur inside the base station.

According to some embodiments, at operation 1 k-15, the base station candeliver a message to request UE capability to the UE, and the concernedmessage may include RAT type and filtering information such asfrequency, or an indicator indicating that the concerned request is toobtain a manufacturer-specific UE capability of the UE. The above UEcapability request message may include a filter to request full UEcapability, or the message may be delivered in an unfiltered state,omitting the filtering information by each RAT type, which may be usedto mean that the full UE capability information should be reported.

In operation 1 k-20, the UE delivers UE capability information inresponse to the UE capability request message to the base station, andthe base station decodes and interprets the concerned receivedinformation to thereby obtain the UE capability. Where an indicatorindicating whether the UE capability information having been received inoperation 1 k-25 is the same as the manufacturer-specific full UEcapability, or a manufacturer-specific identifier of UE capability is inthe received message, the base station determines that the reported UEcapability is the manufacturer-specific full UE capability and can storethe concerned UE capability in the buffer and memory. The received UEcapability information and the indicator information are delivered tothe core network in a NAS message (1 k-30).

Where an indicator indicating whether the UE capability informationhaving been received in operation 1 k-25 is the same as themanufacturer-specific full UE capability, or a manufacturer-specificidentifier of UE capability is not in the received message, the basestation determines that the reported UE capability is not themanufacturer-specific full UE capability and can store the concerned UEcapability in the buffer and memory. The received UE capabilityinformation and the indicator information are delivered to the corenetwork in a NAS message (1 k-40). Even where the concerned message isdelivered, an indicator indicating that the reported UE capability isnot the manufacturer-specific full UE capability may be included. In theillustrative example of FIG. 1K, at operation 1 k-45, if the basestation receives a PLMN-specific identifier of UE capability for theconcerned UE capability from an AMF (core network), the base stationassociates the identifier with the stored UE capability, and stores andmanages them. Thereafter, they are used for configuration with the UE.

FIG. 1L illustrates, in block diagram format, an example of aconfiguration of a UE according various embodiments of this disclosure.

As shown in the illustrative example of FIG. 1L, a UE according to anexemplary embodiment of the disclosure includes a transceiver (1 l-05),a controller (1 l-10), a multiplexing and demultiplexing unit (1 l-15),a variety of uplink processors (1 l-20, 1 l-25), and a control messageprocessor (1 l-30).

The transceiver (1 l-05) receives data and a predetermined controlsignal by a forward channel of a serving cell and transmits the data andthe predetermined control signal by a backward channel. Where aplurality of serving cells are set, the transceiver (1 l-05) performsdata transmission and reception and control signal transmission andreception through the plurality of serving cells. The multiplexing anddemultiplexing unit (1 l-15) plays a role of multiplexing data generatedin the uplink processors (1 l-20, 1 l-25) or the control messageprocessor (1 l-30) or demultiplexing the data received by thetransceiver (1 l-05), and delivering the data to the uplink layerprocessors (1 l-20, 1 l-25) or the control message processor (1 l-30).

According to certain embodiments, the control signal processor (1 l-30)transceives a control message from a base station and conducts anecessary operation therefor. The operation includes a function toprocess the control message such as RRC message and MAC CE, and reportof a CBR measurement value, and reception by UE of resource pool and RRCmessage for an operation. The uplink layer processor (1 l-20, 1 l-25)refers to a DRB device and can be configured by each service. Datagenerated by user services such as FTP (file transfer protocol) or VoIP(voice over Internet protocol) is processed and delivered to themultiplexing and demultiplexing unit (1 l-15), or data delivered fromthe multiplexing and demultiplexing unit (1 l-15) is processed anddelivered to a service application of the uplink layer. The controller(1 l-10) confirms a scheduling instruction received through thetransceiver (1 l-05), for example, backward grants and controls thetransceiver (1 l-05) and the multiplexing and demultiplexing unit (1l-15) so that backward transmission to an appropriate transmissionresource time can be performed at an appropriate.

The disclosure has been described with reference to an example of a UEwhich includes a plurality of blocks and the respective blocks performdifferent functions, which merely constitutes an exemplary embodiment ofthe disclosure, and the disclosure is not limited thereto. For example,a function that is performed by the multiplexing and demultiplexing unit(1 l-15) may be performed by the controller (1 l-10) itself.

FIG. 1M illustrates, in block diagram format, an example a configurationof a base station according to certain embodiments of this disclosure.

Referring to the non-limiting example of FIG. 1M, a base station deviceincludes a transceiver (1 m-05), a controller (1 m-10), a multiplexingand demultiplexing unit (1 m-20), a control message processor (1 m-35),a variety of uplink processors (1 m-25, 1 m-30), and a scheduler (1m-15).

The transceiver (1 m-05) transmits data and a predetermined controlsignal by a forward carrier and receives data and a predeterminedcontrol signals by a backward carrier. Where a plurality of carriers areset, the transceiver (1 m-05) performs data transmission and receptionand control signal transmission and reception through the plurality ofcarriers. The multiplexing and demultiplexing unit (1 m-20) plays a roleof multiplexing data generated in the uplink processors (1 m-25, 1 m-30)or the control message processor (1 m-35) or demultiplexing datareceived by the transceiver (1 m-05), and delivering the data to theproper uplink layer processors (1 m-25, 1 m-30), the control messageprocessor (1 m-35), or the controller (1 m-10).

According to certain embodiments, the control message processor (1 m-35)receives an instruction from the controller and generates a message tobe delivered to the UE, and delivers the message to a downlink layer.The uplink layer processor (1 m-25, 1 m-30) may be constructed by eachUE and each service, and processes data generated by user services suchas FTP or VoIP, etc. and delivers the data to the multiplexing anddemultiplexing unit (1 m-20), or processes data delivered from themultiplexing and demultiplexing unit (1 m-20) and delivers the data to aservice application of the uplink layer. The scheduler (1 m-15) allotsany transmission resource to the UE at appropriate time, inconsideration of buffer state of the UE, channel state, and active timeof the UE, etc., and processes a signal delivered by the UE to thetransceiver or processes the signal so as to be delivered to the UE.

FIG. 2A illustrates an example of a structure of an LTE system,according to various embodiments of this disclosure.

Referring to the non-limiting example of FIG. 2A, a wireless accessnetwork of the LTE system includes a next generation base station(Evolved node B, “eNB”, “Node B” or “base station”) (2 a-05, 2 a-10, 2a-15, 2 a-20), MME (mobility management entity, 2 a-25), and S-GW(serving-gateway, 2 a-30). User equipment (“UE”) (2 a-35) connects to anexternal network via eNB (2 a-05 to 2 a-20) and S-GW (2 a-30).

In FIG. 2A, the eNB (2 a-05 to 2 a-20) corresponds to an existing node Bof the UMTS (Universal Mobile Telecommunication System) system. An eNBis connected to UE (2 a-35) via a wireless channel, performing a morecomplex role than the existing node B. In the LTE system, as all usertraffics including real-time services such as VoIP (voice over IP) viaan Internet protocol are served via a shared channel, a device forcollecting and scheduling state information such as buffer state,available transformation power state, channel state of UEs, etc. isrequired. As such a device, the eNB (2 a-05 to 2 a-20) is used.

According to certain embodiments, one eNB usually controls a number ofcells. In order to realize a transmission speed of 100 Mbps, the LTEsystem uses, for example, orthogonal frequency division multiplexing(“OFDM”) in 20 MHz bandwidth as a wireless accessing technology. Also,the LTE system applies modulation scheme adaptive to the channel stateof the UE and adaptive modulation & coding (“AMC”) to determine achannel coding rate. S-GW (2 a-30) is a device which provides databearer and generates or removes data bearer according to control of MME(2 a-25). MME (2 a-25) is a device which functions various controls aswell as mobility management for a UE.

FIG. 2B illustrates a wireless protocol structure in the LTE system,according to certain embodiments of this disclosure.

Referring to the non-limiting example of FIG. 2B, a wireless protocol ofthe LTE system includes PDCP (packet data convergence protocol) (2 b-05,2 b-40), RLC (radio link control) (2 b-10, 2 b-35), and MAC (mediumaccess control) (2 b-15, 2 b-30) layers at UE and eNB respectively. PDCP(2 b-05, 2 b-40) operates to compress and restore an IP header, etc.Functions of the PDCP layer comprise:

-   -   Header compression and decompression: ROHC only    -   Transfer of user data    -   In-sequence delivery of upper layer PDUs at PDCP        re-establishment procedure for RLC AM    -   For split bearers in DC (only support for RLC AM): PDCP PDU        routing for transmission and PDCP PDU reordering for reception    -   Duplicate detection of lower layer SDUs at PDCP re-establishment        procedure for RLC AM    -   Retransmission of PDCP SDUs at handover and, for split bearers        in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

Radio link control (“RLC”) (2 b-10, 2 b-35) reconstructs PDCP PDU(Packet Data Unit) in appropriate sizes and performs ARQ operation, etc.Functions of the RLC layer comprise:

-   -   Transfer of upper layer PDUs    -   Error Correction through ARQ (only for AM data transfer)    -   Concatenation, segmentation and reassembly of RLC SDUs (only for        UM and AM data transfer)    -   Re-segmentation of RLC data PDUs (only for AM data transfer)    -   Reordering of RLC data PDUs (only for UM and AM data transfer    -   Duplicate detection (only for UM and AM data transfer)    -   Protocol error detection (only for AM data transfer)    -   RLC SDU discard (only for UM and AM data transfer)    -   RLC re-establishment

MAC layer (2 b-15, 2 b-30) is connected to various RLC layer devicesprovided in a UE and performs operations to multiplex RLC PDUs into MACPDUs and demultiplex RLC PDUs from MAC PDUs. Functions of the MAC layercomprise:

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs belonging to one or        different logical channels into/from transport blocks (TB)        delivered to/from the physical layer on transport channels    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

A physical (“PHY”) layer (2 b-20, 2 b-25) operates channel coding andmodulation of upper layer data, to make the data into OFDM symbols andtransmit the OFDM symbols via a wireless channel, and demodulates theOFDM symbols received via the wireless channel, operateschannel-decoding thereof and transmits the decoded data to the upperlink. Also, even in the physical layer, HARQ (hybrid ARQ) is used tocorrect any additional error. Information on whether or not a receiverhas received a packet transmitted from a transmitter has received istransmitted by using 1 bit. This is HARQ ACK/NACK information. DownlinkHARQ ACK/NACK information for the uplink transmission is transmitted viaa physical channel of PHICH (physical hybrid-ARQ indicator channel), anduplink HARQ ACK/NACK information for the downlink transmission may betransmitted via PUCCH (physical uplink control signal) or PUSCH(physical uplink shared channel).

The PHY layer may include one or a plurality of frequencies/carriers. Atechnology to configure and use the plurality of frequenciessimultaneously is called carrier aggregation (“CA”). Only a carrier hasbeen used for communication between a user equipment (UE) and a basestation (E-UTRAN Node B, eNB). However, the CA technology uses one or aplurality of secondary carriers in addition to a primary carrier,thereby being capable of drastically increasing the amount oftransmission according to the number of secondary carriers. In the LTE,the cell in the base station using the primary carrier is PCell (PrimaryCell) and the secondary cell is Scell (Secondary Cell).

In addition, an RRC (radio resource control) layer is present in upperPDCP layers of the UE and the base station respectively, which is notillustrated in the accompanying drawings. The RRC layer can make aconnection for wireless resource control and exchange configurationcontrol messages associated with measurement.

FIG. 2C illustrates an example of a structure of the next generationmobile communication system according to various embodiments of thisdisclosure.

Referring to the illustrative example of FIG. 2C, a wireless accessnetwork of the next generation mobile communication system includes anext generation base station (new radio node B, “NR-NB”) (2 c-10) and anew radio core network or a next generation core network (“NG CN”) (2c-05). A new radio user equipment (“NR UE”) (2 c-15) connects to anexternal network via NR NB (2 c-10) and NR CN (2 c-05).

In the explanatory example of FIG. 2C, the NR NB (2 c-10) corresponds tothe eNB (evolved node B) of the existing LTE system. The NR NB isconnected to NR UE (2 c-15) via a wireless channel and can provide moreexcellent services than the existing node B. In the next generationmobile communication system, as all user traffics are served via ashared channel, a device for collecting and scheduling state informationincluding buffer state, available transmission power state, channelstate, etc. of the UEs is required. As such a device, NR NB (2 c-10) isused. One NR NB usually controls a plurality of cells. To realize ultrahigh speed data transformation as compared with existing LTEs, the NR NBcan have a bandwidth equal to or greater than the existing maximumbandwidth and a beam forming technology can additionally be implementedby using orthogonal frequency division multiplexing (OFDM). Also,adaptive modulation & coding (AMC) to determine a modulation scheme anda channel coding rate adaptive to the channel state of the UE isapplied.

According to certain embodiments, a NR CN (2 c-05) functions to supportmobility and set up bearer and QoS, etc. The NR CN is a device providinga variety of controls as well as mobility management for the UE and isconnected to a number of base stations. Also, the next generation mobilecommunication system can be associated with the existing LTE system, andthe NR CN is connected to MME (2 c-25) via a network interface. MME isconnected to eNB (2 c-30) which is an existing base station.

FIG. 2D illustrates an example of a wireless protocol structure of thenext generation mobile communication system according to variousembodiments of this disclosure.

Referring to the explanatory example of FIG. 2D, a wireless protocol ofthe next generation mobile communication system includes NR SDAP (2d-01, 2 d-45), NR PDCP (2 d-05, 2 d-40), NR RLC (2 d-10, 2 d-35), and NRMAC (2 d-15, 2 d-30) at UE and NR base station respectively.

Functions of the NR SDAP (2 d-01, 2 d-45) comprise one or more of thefollowing:

-   -   Transfer of user plane data    -   Mapping between a QoS flow and a DRB for both DL and UL    -   Marking QoS flow ID in both DL and UL packets    -   Reflective QoS flow to DRB mapping for the UL SDAP PDUs

With respect to an SDAP layer device, a UE can receive setup as towhether to use a header of the SDAP layer device by each PDCP layerdevice, each bearer, or each logical channel, or to use a function ofthe SDAP layer device, by means of the RRC message. Where the SDAPheader is set, the SDAP layer device can instruct the UE to update orreset QoS flows of the uplink and the downlink and mapping informationfor data bearer by a 1-bit NAS reflective QoS indicator and a 1-bit ASreflective QoS indicator of the SDAP header. The SDAP header may includeQoS flow ID information representing QoS. The QoS information may beused as data processing priority, scheduling information, etc. to assistin smooth services.

Functions of NR PDCP (2 d-05, 2 d-40) can include one or more of thefollowing:

-   -   Header compression and decompression: ROHC only    -   Transfer of user data    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   PDCP PDU reordering for reception    -   Duplicate detection of lower layer SDUs    -   Retransmission of PDCP SDUs    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

Reordering function of the NR PDCP device is a function to sequentiallyreorder PDCP PDUs received by the lower layer based on PDCP SN (sequencenumber). This function may include a function to transmit data to theupper layer in the reordered sequence or to directly transmit datawithout considering the sequence, and a function to record lost PDCPPDUs by reordering the sequence thereof. In addition, functions toreport states of the lost PDCP PDUs to the transmitter, and to requestretransmission of the lost PDCM PDUs may be included.

Functions of NR RLC (2 d-10, 2 d-35) include one or more of thefollowing:

-   -   Transfer of upper layer PDUs    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   Error Correction through ARQ    -   Concatenation, segmentation and reassembly of RLC SDUs    -   Re-segmentation of RLC data PDUs    -   Reordering of RLC data PDUs    -   Duplicate detection    -   Protocol error detection    -   RLC SDU discard    -   RLC re-establishment

Referring to the illustrative example of FIG. 2d , in-sequence deliveryof the NR RLC device is a function to transmit RLC SDUs received fromthe lower layer to the upper layer in sequence, originally where one RLCSDU is segmented into several RLC SDUs and the segmented RLC SDUs arereceived, a function to reassemble and transmit the received RLC PDUsmay be included. A function to reorder the received RLC PDUs based onRLC SN or PDCP SN, a function to reorder the sequence of the receivedRLC PDUs and record lost RLC PDUs, a function to report the states ofthe lost RLC PDUs to the transmitter, and a function to requestretransmission of the lost RLC PDUs may also be included. Where there isany lost RLC SDU, a function to transmit only the RLC SDUs prior to thelost RLC SDU to the upper layer in sequence may be included. In certainembodiments, where a predetermined timer expires even though there isany lost RLC SDU, a function to transmit all the RLC SDUs receivedbefore the timer starts to the upper layer in sequence may be included.Where a predetermined timer expires even though there is any lost RLCSDU, a function to transmit all the RLC SDUs received up to now to theupper layer in sequence may be included. Also, the RLC PDUs may beprocessed in the order as they are received (in the order as arrived,without regard to the sequence of serial numbers, sequence numbers,etc.) and delivered to the PDCP device without regard to the sequence(out-of sequence delivery). In case of segments, segments are stored ina buffer or segments to be received later are received and thereafterthey are reconstructed into a complete single RLC PDU, which is thenprocessed and delivered to the PDCP device. The NR RLC layer may notinclude a function of concatenation, or this function may be performedat the NR MAC layer or substituted for a multiplexing function of the NRMAC layer.

According to certain embodiments, an out-of sequence delivery functionof the NR RLC device is a function to deliver the RLC SDUs received fromthe lower layer directly to the upper layer without regard to thesequence thereof. Where an originally single RLC SDU is segmented intoseveral RLC SDUs and the segmented RLC SDUs are received, a function toreassemble them may be included. A function to store RLC SNs or PDCP SNsof the received RLC PDUs and order them in sequence, and record lost RLCPDUs may also be included.

Referring to the non-limiting example of FIG. 2D, NR MAC (2 d-15, 2d-30) can be connected to several NR RLC layer devices included in a UE.Functions of an NR MAC include one or more of the following:

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

According to various embodiments, an NR PHY layer (2 d-20, 2 d-25) canoperate channel coding and modulation of upper layer data, make theminto OFDM symbols and transmit the OFDM symbols via a wireless channel,and demodulate the OFDM symbols received via the wireless channel,operate channel-decoding thereof and transmit the decoded data to theupper link.

FIG. 2E illustrates an example of procedures by which a base stationtransmits cell-based uplink configuration to the UE and thereafterreleases the specific uplink configuration, according to variousembodiments of this disclosure.

Referring to the non-limiting example of FIG. 2E, UE (2 e-01) in an RRCIDLE state is camped on after passing through a cell selection procedurefor a specific base station (2 e-02) and can receive system information.Thereafter, the UE performs an RRC connection procedure with theconcerned cell in operation 2 e-05 and the UE in the RRC connectionstate is shifted to the concerned cell. According to variousembodiments, at operation 2 e-10, a base station delivers anRRCReconfiguration message to the UE and provides configurationinformation applied to the UE in the concerned cell. The message mayinclude, in particular, ServingCellConfigCommon, which is the basicinformation in the concerned serving cell, and ServingCellConfigconfiguration information which is specific information based on UE inthe concerned cell. In particular, if the base station supports theconcerned cell, configuration information for a normal uplink(hereinafter referred to as “NUL”) and a supplementary uplink(hereinafter referred to as “SUL”) may be included in in theServingCellConfigCommon. The concerned configuration information isconfiguration information delivered to all UEs in the cell if the basestation supports them on a cell basis. An example of ASN.1 code forimplementing the above-described functionality is provided below:

ServingCellConfigCommon ::=  SEQUENCE {  physCellId PhysCellId OPTIONAL, -- Cond HOAndServCellAdd,  downlinkConfigCommon DownlinkConfigCommon OPTIONAL, -- Cond InterFreqHOAndServCellAdd uplinkConfigCommon UplinkConfigCommon  OPTIONAL, -- Need M supplementaryUplinkConfig UplinkConfigCommon OPTIONAL, -- Need S n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 }  OPTIONAL,--Need S  ssb-PositionsInBurst  CHOICE {  shortBitmap  BIT STRING (SIZE(4)),  mediumBitmap BIT STRING (SIZE (8)),  longBitmap  BIT STRING (SIZE(64))  } OPTIONAL, -- Cond AbsFreqSSB  ssb-periodicityServingCellENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need S  dmrs-TypeA-Position  ENUMERATED {pos2, pos3}, lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE- CRS }OPTIONAL,  -- Need M rateMatchPatternToAddModList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF OPTIONAL, -- Need N RateMatchPatternId subcarrierSpacing  SubcarrierSpacing  OPTIONAL, -- Need S tdd-UL-DL-ConfigurationCommon  TDD-UL-DL- ConfigCommon  OPTIONAL, --Cond TDD  ss-PBCH-BlockPower INTEGER (−60..50),  ... }

SupplementaryUplinkConfig

According to certain embodiments, this field is optionally present ifUplinkConfigcomon is set but is not present in any other cases. Wherethis field is not present, the UE releases SupplementaryUplinkConfig ifset in ServingCellConfig.

Also, in some embodiments, the ServingCellConfigCommon may be includedwhen it is delivered to a target cell from the previous cell at the timeof handover. In this case, where the UE having received support of NUL(normal UL) and SUL (supplementary UL) in the previous serving cell ishanded over to a serving cell which supports only NUL, the configurationinformation for SUL may be released. That is, thesupplementaryUplinkConfg is discarded from the ServingCellConfigCommon,the UE releases SUL configuration information.

However, under current standards, serving cells support both NUL andSUL, and there is no function to set only one UL for a specific UE. Thatis, where the UE is isolated from a cell edge (moves to the center of acell), SUL configuration is not required, and support for more featuresmay be wanted. Also, where SUL is set, as capability limitation (forexample, limitation to UL MIMO, etc.) may be applied to the UE, andthus, more UE capability and wireless features can be used if NUL issolely set than in the case of NUL+SUL configuration. The non-limitingexample of ASN.1 code shown below indicates that current standardscannot release SUL for a specific UE. That is, a SupplementaryUplinkfield is set to OPTIONAL NEED M in the ASN.1 code. This means that wherethe concerned filed is discarded and delivered in the nextconfiguration, if there is a value set previously, the previous value ismaintained. That is, although NUL and SUL are simultaneously set in theprevious RRC configuration, and SUL is discarded and delivered in thenext configuration, it does not mean release of SUL.

ServingCellConfig ::= SEQUENCE {  tdd-UL-DL-ConfigurationDedicatedTDD-UL-DL- ConfigDedicated  OPTIONAL, -- Cond TDD initialDownlinkBWPBWP- DownlinkDedicated OPTIONAL, -- Need M downlinkBWP-ToReleaseListSEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need NdownlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OFBWP-Downlink  OPTIONAL, -- Need N firstActiveDownlinkBWP-Id BWP- IdOPTIONAL, -- Cond SyncAndCellAdd  bwp-InactivityTimer  ENUMERATED {ms2,ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,  ms40,ms50, ms60, ms80,ms100,ms200,ms300, ms500, ms750, ms1280, ms1920, ms2560, spare10, spare9,spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }OPTIONAL, --Need R defaultDownlinkBWP-Id BWP- Id  OPTIONAL, -- Need S uplinkConfig UplinkConfig  OPTIONAL, -- Need M  supplementaryUplink UplinkConfig OPTIONAL, -- Need M pdcch-ServingCellConfig  SetupRelease{ PDCCH- ServingCellConfig } OPTIONAL, -- Need M pdsch-ServingCellConfig SetupRelease { PDSCH- ServingCellConfig } OPTIONAL, -- Need Mcsi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, -- Need M sCellDeactivationTimer  ENUMERATED {ms20, ms40, ms80, ms160, ms200,ms240, ms320, ms400, ms480, ms520, ms640, ms720,  ms840,  ms1280,spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCH crossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, --Need M  tag-Id TAG-Id,  ue-BeamLockFunction ENUMERATED {enabled}OPTIONAL, -- Need R pathlossReferenceLinking  ENUMERATED {pCell, sCell}OPTIONAL, -- Cond SCellOnly  servingCellMO  MeasObjectId  OPTIONAL, --Cond MeasObject  ...,  [[  lte-CRS-ToMatchAround  SetupRelease {RateMatchPatternLTE- CRS } OPTIONAL, -- Need MrateMatchPatternToAddModList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE(1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N downlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OFSCS-SpecificCarrier OPTIONAL -- Need S  ]] }

Referring to the non-limiting example of FIG. 2E, at operation 2 e-15,the UE can measure serving cells and cells of the serving frequency, andcells of peripheral frequency and other RAT according to the measurementprocedure, and includes the measurement results in a measurementreporting message so as to be then delivered to the base station. Inoperation 2 e-20, the base station interprets information of thereceived measurement report of the UE and can know that the current cellis not present in the cell edge but is present near the center of theserving cell. That is, this may be a case where the serving cellmeasurement value of the UE is good. In this case, the base station candetermine to release SUL having been set for the concerned UE. This isto allow the UE to use more UE capability and provide more wirelessresources.

In operation 2 e-25, the base station includes ReconfigurationWithSyncand ServingCellConfigCommon including configuration information only forthe uplink (NUL) in an RRCReconfiguration message and can deliver themessage to the UE. According to this configuration information, the UEis instructed to re-perform synchronous configuration via random access,release SUL configuration from the concerned cell, and apply only theNUL configuration. In operation 2 e-30, the UE applies the configurationfor the set NUL, performs a random access procedure for the concernedcell, and obtains uplink and downlink synchronization. In operation 2e-35, the UE performs data transmission and reception with the basestation. In this case, the new configuration value received in operation2 e-25 is applied, SUL configuration is released, and communication isconducted by applying only NUL.

In particular, the disclosure features that SUL is not set for aspecific UE although the concerned serving sell supports both NUL andSUL. Under current standards, cell-based uplink configurationinformation is continuously provided from ServingCellConfigCommon andServingCellConfigCommonSIB according to the support thereof by the cell.However, if the disclosure is applied, SUL configuration information maybe absent for a specific UE, separately from the cell capability. If thebase station delivers ServingCellConfigCommon from which SULconfiguration is discarded, together from ReconfigurationWithSync, theUE releases the SUL configuration information present inServingCellConfig, which is a dedicated RRC message.

In certain embodiments, even though the UE receives again SIM (that is,both NUL and SUL configurations are included inServingCellConfigCommonSIB) supplied from the base station after havingperformed the concerned procedure, the SUL cannot be used again becauseSUL configuration information included in the dedicated message has beenreleased. Currently, ReconfigurationWithSync configuration is used in acase of changing PCell (handover), in which the most important systeminformation in the target cell can be included. The disclosure featuresthat if the disclosure is applied, a method of usingReconfigurationWithSync is applied for a cell-based UE.

FIG. 2F illustrates an example of operations by the UE when release ofthe UE-based uplink in a specific cell is applied, as provided in thedisclosure.

Referring to the non-limiting example of FIG. 2F, a UE in a RRC IDLEstate is camped on after passing through a cell selection procedure fora specific base station, and can receive system information. Thereafter,the UE performs an RRC connection procedure with the concerned cell andis shifted to the concerned cell in the RRC connection state. Inoperation 2 f-05, the UE receives an RRCReconfiguration message from thebase station and receives configuration information applied to the UE inthe concerned cell. The message may include ServingCellConfigCommonwhich is the basic information in the concerned cell andServingCellConfig configuration information which is specificinformation based on the UE. In particular, if the base station supportsthe concerned cell, configuration information for the normal uplink(NUL) and the supplementary uplink (SUL) may be included inServingCellConfigCommon. The concerned configuration information isconfiguration information delivered to all UEs in the cell if supportedby the base station on a cell basis.

According to certain embodiments, at operation 2 f-10, the UE canmeasure serving cells, cells of serving frequencies, and cells ofperipheral frequencies and other RAT cells according to the measurementprocedure. In operation 2 f-15, the UE can receive an RRCReconfigurationmessage delivered from the base station, and ReconfigurationWithSync andServingCellConfigCommon having only the uplink configuration informationcan be included in the concerned message. According to thisconfiguration information, the UE is instructed to re-performsynchronous configuration via random access, release SUL configurationfrom the concerned cell, and apply only the NUL configuration. Inoperation 2 f-20, the UE applies the configuration for the set NUL,performs a random access procedure for the concerned cell, and obtainsuplink and downlink synchronization. In operation 2 f-25, the UEperforms data transmission and reception with the base station. In thiscase, the new configuration value received in operation 2 f-15 isapplied, SUL configuration is released, and communication is conductedby applying only NUL.

FIG. 2G illustrates an example of operations by the base station when amethod to release the UE-based uplink in a specific cell is applied,according to various embodiments of this disclosure.

Referring to the non-limiting example of FIG. 2G, a UE in an RRC IDLEstate is camped on after passing through the cell selection procedurefor a specific base station and performs an RRC connection procedurewith the concerned cell after having received the system information.The base station shifts the concerned UE to the RRC connection state. Inoperation 2 g-05, the base station delivers an RRCReconfigurationmessage to the UE and provides configuration information applied to theUE in the concerned cell. The message may include, in particular,ServingCellConfigCommon which is the basic information in the concernedserving cell and ServingCellConfig configuration information which isspecific information based on UE in the concerned cell. In particular,if the base station supports the concerned cell, configurationinformation for a normal uplink (hereinafter referred to as “NUL”) and asupplementary uplink (hereinafter referred to as “SUL”) may be includedin the ServingCellConfigCommon. The concerned configuration informationis configuration information delivered to all UEs in the cell if thebase station supports them on a cell basis.

According to certain embodiments, at operation 2 g-10, the base stationreceives a measurement report delivered by the UE. The measurementreport may include measurement values of serving cells, cells of servingfrequency, and cells of peripheral frequency and other RATs according tothe measurement procedure. In operation 2 g-15, the base stationinterprets information of the received measurement of the UE and canknow that the current UE is not present in the cell edge but is presentnear the center of the serving cell. That is, this may be a case wherethe measurement value for the serving cell of the UE is good. In thiscase, the base station can determine to release SUL set for theconcerned UE. This is to allow the UE to use more UE capability and toprovide more wireless resources.

In operation 2 g-20, the base station sets an RRCREconfiguration messageand delivers the message to the UE for configuring the UE withdetermination at the above operation. The concerned message may includeReconfigurationWithSync and ServingCellConfigCommon having only theuplink (NUL) configuration information. According to this configurationinformation, the UE is instructed to re-perform synchronousconfiguration via random access, release SUL configuration from theconcerned cell, and apply only the NUL configuration. In operation 2g-25, the UE applies the configuration for the set NUL and performs arandom access procedure for the concerned cell, and the base stationperforms the concerned random access procedure. In operations 2 f-30,the base station and the UE perform data transmission and reception.

FIG. 2H illustrates, in block diagram format, an example of an internalstructure of the UE according to certain embodiments of this disclosure.

Referring to the non-limiting example of FIG. 2H, a UE includes an RF(radio frequency) processor (2 h-10), a baseband processor (2 h-20), astorage (2 h-30), and a controller (2 h-40).

According to various embodiments RF processor (2 h-10) performs afunction to transceive signals for band conversion of the signal,amplification, etc. via a wireless channel. That is, the RF processor (2h-10) performs upward transformation of a baseband signal provided fromthe baseband processor (2 h-20) into an RF band signal and thereaftertransmits the RF band signal through an antenna, and performs downwardtransformation of the RF band received through the antenna signal into abaseband signal. For example, the RF processor (2 h-10) may include atransmission filter, a reception filter, an amplifier, a mixer, anoscillator, a DAC (digital to analog convertor), an ADC (analog todigital convertor), etc. FIG. 2H shows only one antenna, but the UE maybe provided with a plurality of antennas. Also, the RF processor (2h-10) may include a plurality of RF chains. Further, the RF processor (2h-10) can perform beamforming. For the beamforming, the RF processor (2h-10) can adjust phases and sizes of respective signals transceivedthrough the plurality of antennas or antenna elements. Also, the RFprocessor can perform MIMO and can receive plural layers when the MIMOoperation is performed.

According to some embodiments, baseband processor (2 h-20) performstransformation between baseband signal and bitstream according to thephysical layer specification of the system. For example, when data istransmitted, the baseband processor (2 h-20) encodes and modulates thetransmitted bitstream, thereby generating complex symbols. Also whendata is received, the baseband processor (2 h-20) demodulates anddecodes the baseband signal provided from the RF processor (2 h-10),thereby restoring the received bitstream. For example, according to theOFDM (orthogonal frequency division multiplexing) method, when data istransmitted, the baseband processor (2 h-20) encodes and modulates thetransmitted bitstream, thereby generating complex symbols. After mappingthe complex symbols with subcarriers, the baseband processor (2 h-20)constructs OFDM symbols through IFFT (inverse fast Fourier transform)operation and CP (cyclic prefix) insertion. Also when data is received,the baseband processor (2 h-20) segments the baseband signal providedfrom the RF processor (2 h-10) in the unit of OFDM symbols. Afterrestoring signals mapped with the subcarriers through FFT (fast Fouriertransform) operation, the baseband processor (2 h-20) restores thereceived bitstream through demodulation and decoding.

As described above, the baseband processor (2 h-20) and the RF processor(2 h-10) transceive signals. Accordingly, the baseband processor (2h-20) and the RF processor (2 h-10) may be referred to as a transmitter,a receiver, a transceiver or a communicator. Further, at least one ofthe baseband processor (2 h-20) and the RF processor (2 h-10) mayinclude a plurality of communication modules so as to support a numberof different wireless connection technologies. Also, at least one of thebaseband processor (2 h-20) and the RF processor (2 h-10) may includethe different communication modules so as to process signals ofdifferent frequency bands. For example, the different wirelessconnection technologies may include wireless LAN (e.g., IEEE 802.11),cellular network (e.g., LTE), etc. Also, the different frequency bandsmay include super high frequency (SHF) (e.g., 2.NRHz, NRhz) bands andmillimeter (MM) wave (e.g., 60 GHz) bands.

As shown in the illustrative example of FIG. 2H, storage (2 h-30) storesbasic programs for operation of the UE, application programs and datasuch as configuration information. The storage (2 h-30) may storeinformation associated with a second connection node that performswireless communication by use of a second wireless connectiontechnology. Also, the storage (2 h-30) provides the stored dataaccording to request from the controller (2 h-40).

The controller (2 h-40) controls general operations of the UE. Forexample, the controller (2 h-40) transceives signals through thebaseband processor (2 h-20) and the RF processor (2 h-10). Also, thecontroller (2 h-40) records data on the storage (2 h-30) and reads thedata. For this, the controller (2 h-40) may include at least oneprocessor. For example, the controller (2 h-40) may include a CP(communication processor) that performs control for communication and anAP (application processor) that controls upper layers such asapplication programs.

FIG. 2I illustrates, in block diagram format, an example of aconfiguration of the base station according to various embodiments ofthis disclosure.

Referring to the non-limiting example of FIG. 2I, the base stationincludes an RF processor (2 i-10), a baseband processor (2 i-20), abackhaul communicator (2 i-30), a storage (2 i-40), and a controller (2i-50).

In certain embodiments, the RF processor (2 i-10) functions totransceive signals for band change of signals and amplification, etc.via a wireless channel. That is, the RF processor (2 i-10) performsupward transformation of a baseband signal provided from the basebandprocessor (2 i-20) into an RF band signal and transmits the RF bandsignal through an antenna, and performs downward transformation of an RFband signal received through the antenna into a baseband signal. Forexample, the RF processor (2 i-10) may include a transmission filter, areception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC,etc. In FIG. 2I, only one antenna is illustrated, but a first connectionnode may have a plurality of antennas. Also, the RF processor (2 i-10)may include a plurality of RF chains. Further, the RF processor (2 i-10)can perform beamforming. For the beamforming, the RF processor (2 i-10)can adjust phases and sizes of respective signals transceived throughthe plurality of antennas or antenna elements. Also, the RF processorcan perform downward MIMO operating by transmitting one or more layers.

In certain embodiments, baseband processor (2 i-20) performs atransformation between the baseband signal and bitstream according tothe physical layer specification of a first wireless connectiontechnology. For example, when data is transmitted, the basebandprocessor (2 i-20) encodes and modulates the transmitted bitstream,thereby generating complex symbols. Also when data is received, thebaseband processor (2 i-20) demodulates and decodes the baseband signalprovided from the RF processor (2 i-10), thereby restoring the receivedbitstream. For example, according to the OFDM (orthogonal frequencydivision multiplexing) method, when data is transmitted, the basebandprocessor (2 i-20) encodes and modulates the transmitted bitstream,thereby generating complex symbols. After mapping the complex symbolswith subcarriers, the baseband processor (2 i-20) constructs OFDMsymbols through IFFT (inverse fast Fourier transform) operation and CP(cyclic prefix) insertion. Also when data is received, the basebandprocessor (2 i-20) segments the baseband signal provided from the RFprocessor (2 i-10) in the unit of OFDM symbols. After restoring signalsmapped with the subcarriers through a FFT (fast Fourier transform)operation, the baseband processor (2 i-20) restores the receivedbitstream through demodulation and decoding. As described above, thebaseband processor (2 i-20) and the RF processor (2 i-10) transceivesignals. Accordingly, the baseband processor (2 i-20) and the RFprocessor (2 i-10) may be referred to as a transmitter, a receiver, atransceiver, a communicator or a wireless communicator.

According to various embodiments, backhaul communicator (2 i-30)provides an interface for performing communication with other nodes inthe network. That is, the backhaul communicator (2 i-30) transformsbitstream transmitted from a primary base station to any other node, forexample, to a supplementary base station, a core network, etc. intophysical signals, and physical signals received from the other node aretransformed into bitstream.

The storage (2 i-40) stores basic programs for operation of the primarybase station, application programs and data such as configurationinformation. In particular, the storage (2 i-40) may store informationassociated with a bearer allotted to the connected UE, measurementresults reported from the connected UE, etc. Also, the storage (2 i-40)may provide multiple connection to the UE or store information that canbe a basis to determine interruption of the connection. The storage (2i-40) also provides stored data at the request from the controller (2i-50).

The controller (2 i-50) controls general operations of the primary basestation. For example, the controller (2 i-50) transceives signalsthrough the baseband processor (2 i-20) and the RF processor (2 i-10) orthe backhaul communicator (2 i-30). Also, the controller (2 i-50)records data on the storage (2 i-40) and reads the data. For this, thecontroller (i-50) may include at least one processor.

In the above-described detailed embodiments of the disclosure, anelement included in the disclosure is expressed in the singular or theplural according to presented detailed embodiments. However, thesingular form or plural form is selected appropriately to the presentedsituation for the convenience of description, and the disclosure is notlimited by elements expressed in the singular or the plural. Therefore,either an element expressed in the plural may also include a singleelement or an element expressed in the singular may also includemultiple elements.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method performed by a terminal in a wirelesscommunication system, the method comprising: receiving, from a basestation, a message including configuration information on an uplink (UL)for a cell of the base station and configuration information on asupplementary uplink (SUL) for a cell of the base station; communicatingwith the base station on the UL or the SUL, based on the configurationinformation on the UL or the configuration information on the SUL;receiving, from the base station, a radio resource control (RRC)reconfiguration message; and releasing the SUL, in case that the RRCreconfiguration message does not include information associated with aSUL configuration.
 2. The method of claim 1, wherein the RRCreconfiguration message includes reconfigurationwithsync configuration.3. The method of claim 1, wherein the message is a system informationblock (SIB) type 1 message or an RRC reconfiguration message.
 4. Themethod of claim 1, wherein a communication with the base station on theSUL is not performed, in case that a system information block type 1(SIB1) including the configuration information on the UL for the cell ofthe base station and the configuration information on the SUL for thecell of the base station is received from the base station, afterreleasing the SUL.
 5. A method performed by a base station in a wirelesscommunication system, the method comprising: transmitting, to aterminal, a message including configuration information on an uplink(UL) for a cell of the base station and configuration information on asupplementary uplink (SUL) for a cell of the base station; communicatingwith the terminal on the UL or the SUL, based on the configurationinformation on the UL or the configuration information on the SUL; andtransmitting, to the terminal, a radio resource control (RRC)reconfiguration message, wherein the SUL is released, in case that theRRC reconfiguration message does not include information associated witha SUL configuration.
 6. The method of claim 5, wherein the RRCreconfiguration message includes reconfigurationwithsync configuration.7. The method of claim 5, wherein the message is a system informationblock (SIB) type 1 message or an RRC reconfiguration message.
 8. Themethod of claim 5, wherein a communication with the terminal on the SULis not performed, in case that a system information block type 1 (SIB1)including the configuration information on the UL for the cell of thebase station and the configuration information on the SUL for the cellof the base station is transmitted to the terminal, after releasing theSUL.
 9. A terminal in a wireless communication system, the terminalcomprising: a transceiver; and a controller configured to: receive, viathe transceiver from a base station, a message including configurationinformation on an uplink (UL) for a cell of the base station andconfiguration information on a supplementary uplink (SUL) for a cell ofthe base station, communicate with the base station on the UL or theSUL, based on the configuration information on the UL or theconfiguration information on the SUL, receive, via the transceiver froma base station, a radio resource control (RRC) reconfiguration message;and release the SUL, in case that the RRC reconfiguration message doesnot include information associated with a SUL configuration.
 10. Theterminal of claim 9, wherein the RRC reconfiguration message includesreconfigurationwithsync configuration.
 11. The terminal of claim 9,wherein the message is a system information block (SIB) type 1 messageor an RRC reconfiguration message.
 12. The terminal of claim 9, whereina communication with the base station on the SUL is not performed, incase that a system information block type 1 (SIB1) including theconfiguration information on the UL for the cell of the base station andthe configuration information on the SUL for the cell of the basestation is received from the base station, after releasing the SUL. 13.A base station in a wireless communication system, the base stationcomprising: a transceiver; and a controller configured to: transmit, viathe transceiver to a terminal, a message including configurationinformation on an uplink (UL) for a cell of the base station andconfiguration information on a supplementary uplink (SUL) for a cell ofthe base station, communicate with the terminal on the UL or the SUL,based on the configuration information on the UL or the configurationinformation on the SUL, and transmit, via the transceiver to theterminal, a radio resource control (RRC) reconfiguration message,wherein the SUL is released, in case that the RRC reconfigurationmessage does not include information associated with a SULconfiguration.
 14. The base station of claim 13, wherein the RRCreconfiguration message includes reconfigurationwithsync configuration.15. The base station of claim 13, wherein the message is a systeminformation block (SIB) type 1 message or an RRC reconfigurationmessage.
 16. The base station of claim 13, wherein a communication withthe terminal on the SUL is not performed, in case that a systeminformation block type 1 (SIB1) including the configuration informationon the UL for the cell of the base station and the configurationinformation on the SUL for the cell of the base station is transmittedto the terminal, after releasing the SUL.